Skip to content

CCDR: Note remote address resolution is possible#3069

Open
DanGooding wants to merge 1 commit into
neo4j:devfrom
DanGooding:ccdr/add-remote-address-resolution
Open

CCDR: Note remote address resolution is possible#3069
DanGooding wants to merge 1 commit into
neo4j:devfrom
DanGooding:ccdr/add-remote-address-resolution

Conversation

@DanGooding
Copy link
Copy Markdown

@DanGooding DanGooding commented May 14, 2026

Document that cross-cluster database replication is possible even with disjoint allocation, where not every upstream server hosts the upstream database.

We consider this to be the expected default behaviour from customers, so don't want to have too much detail on how or why there is no restriction about upstream allocations, so as not to expose implementation details.

For some more context: we've just implemented remote-address-resolution for replica databases, which (similarly to backups) lets the replica select which upstream servers to pull from. Previously, the replica would fail to create/fail to pull if some upstream server didn't host the upstream database.

Part of CLUSTER-1367

@DanGooding DanGooding force-pushed the ccdr/add-remote-address-resolution branch from 6f03244 to 2882472 Compare May 14, 2026 14:44
@DanGooding DanGooding marked this pull request as draft May 14, 2026 14:45
@DanGooding DanGooding force-pushed the ccdr/add-remote-address-resolution branch from 2882472 to a0c3c8c Compare May 14, 2026 14:57
@neo4j-docops-agent
Copy link
Copy Markdown
Collaborator

This PR includes documentation updates
View the updated docs at https://neo4j-docs-operations-3069.surge.sh

Updated pages:

@DanGooding DanGooding marked this pull request as ready for review May 14, 2026 15:05
@DanGooding DanGooding changed the title CCDR: Describe remote address resolution CCDR: Note remote address resolution is possible May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants